-
Notifications
You must be signed in to change notification settings - Fork 10
Use set_valid_worlds! instead of manual optimisation #205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Libtask.jl documentation for PR #205 is available at: |
|
After some optimisations provided by @Technici4n, the benchmarks on this branch are now on par with That makes this ready for review. |
sunxd3
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks clean
|
great work, both! |
|
This really all @Technici4n, I just copied over some of his code from Mooncake/Slack and added comments. Thank you! |
|
I think something here broke Turing: https://github.com/TuringLang/Turing.jl/actions/runs/19153277686/job/54748336850?pr=2710 |
Replicating the changes made to Mooncake by in chalk-lab/Mooncake.jl#832.
The benchmarks that pass, run on this branch:
on
main:and on
mainbut skipping the manual optimisation and just callingmisty_closuredirectly:Two of these are close, but the Rosenbrock one is 230% slower and matrix_test about 60% slower on this branch, and very similar to if I just disable the manual optimisation.